-
Notifications
You must be signed in to change notification settings - Fork 17
Release/1.2.42 #586
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release/1.2.42 #586
Conversation
WalkthroughThis PR updates the package to v1.2.42: bumps ably-cocoa to 1.2.53, raises example iOS deployment target to 12.0, adds several Firebase/Google frameworks to the example Xcode project embedding configuration, and documents a fix for a crash when HTTPS responses return 404. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro Disabled knowledge base sources:
📒 Files selected for processing (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
🔇 Additional comments (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
example/ios/Podfile (1)
37-47: Critical: Inconsistent iOS deployment target in post_install hook.Line 44 sets
IPHONEOS_DEPLOYMENT_TARGET = '10.0', which conflicts with the platform declaration at line 2 (platform :ios, '12.0'). This override will cause generated projects to target iOS 10.0, negating the platform update.Apply this diff to align the deployment target:
project.targets.each do |target| target.build_configurations.each do |config| - config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '10.0' + config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.0' end end
🧹 Nitpick comments (1)
CHANGELOG.md (1)
3-9: Consider documenting additional changes in the changelog.The changelog correctly documents the ably-cocoa update and 404 crash fix. However, two significant changes are not mentioned:
- iOS deployment target raised from 10.0 to 12.0 (visible in
example/ios/Podfileand project configuration)- Firebase-related frameworks now embedded as transitive dependencies (visible in
example/ios/Runner.xcodeproj/project.pbxproj)Users upgrading to this version should be aware of the iOS 12.0 minimum requirement.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Jira integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (5)
example/ios/Podfile.lockis excluded by!**/*.lockexample/pubspec.lockis excluded by!**/*.lockpubspec.lockis excluded by!**/*.locktest_integration/ios/Podfile.lockis excluded by!**/*.locktest_integration/pubspec.lockis excluded by!**/*.lock
📒 Files selected for processing (6)
CHANGELOG.md(1 hunks)README.md(1 hunks)example/ios/Podfile(1 hunks)example/ios/Runner.xcodeproj/project.pbxproj(1 hunks)ios/ably_flutter.podspec(1 hunks)pubspec.yaml(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
- GitHub Check: build
- GitHub Check: android (24)
- GitHub Check: android (29)
- GitHub Check: ios
- GitHub Check: check
- GitHub Check: android
- GitHub Check: ios
🔇 Additional comments (6)
pubspec.yaml (1)
3-3: Version bump looks correct.The version update to 1.2.42 is consistent with the CHANGELOG and README documentation.
example/ios/Podfile (1)
2-2: iOS deployment target bumped to 12.0.This aligns with the dependency update to ably-cocoa 1.2.53.
README.md (1)
57-57: Documentation updated correctly.The installation instruction reflects the new version 1.2.42.
ios/ably_flutter.podspec (2)
21-21: Ably CocoaPod dependency updated correctly.The update from 1.2.33 to 1.2.53 addresses the 404 crash issue documented in the CHANGELOG.
23-23: Based on codebase inspection, the review comment identifies a real configuration inconsistency, though it's more complex than stated:Actual inconsistency found:
ios/ably_flutter.podspecline 23 setss.ios.deployment_target = '10.0'example/ios/Podfileline 2 setsplatform :ios, '12.0'- However,
example/ios/Podfilepost_install hook overrides this to'10.0', creating internal contradiction in the example Podfile itselfThe codebase indeed specifies
Ablyversion1.2.53as a dependency (podspec line 22). The core issue is that iOS 10.0 deployment target may be incompatible with Ably 1.2.53, which could have a higher minimum requirement. Without access to the CocoaPods spec for Ably 1.2.53, the exact minimum iOS version cannot be verified from within the sandbox.Please verify:
- Check Ably CocoaPod 1.2.53 minimum iOS deployment target by visiting CocoaPods.org or running
pod spec cat Ablyin your local environment- If Ably 1.2.53 requires iOS 12.0+, update both
ios/ably_flutter.podspec(line 23) andexample/ios/Podfile(line 2 and post_install hook line) to use consistent iOS 12.0- If Ably 1.2.53 supports iOS 10.0, update
example/ios/Podfileline 2 to match the podspec's 10.0, as the post_install hook already sets it correctlyexample/ios/Runner.xcodeproj/project.pbxproj (1)
223-265: Firebase frameworks added as transitive dependencies.These frameworks (FirebaseCore, FirebaseCoreInternal, FirebaseInstallations, FirebaseMessaging, GoogleDataTransport, GoogleUtilities, FBLPromises, Toast, nanopb) are embedded by CocoaPods, likely as transitive dependencies of Ably 1.2.53. This is auto-generated and expected behavior.
Summary by CodeRabbit
Bug Fixes
Chores
Documentation